Home
Installing
An HCL Launch installation consists of the HCL Launch server, a database, and at least one agent.
Installing with Kubernetes
The HCL Launch server can be installed in a cloud-based environment, as a containerized server cluster, managed by Kubernetes. HCL Launch works with Kubernetes to simplify application deployment and manage versions in the containers.
Accessing the HCL Launch server in a Kubernetes cluster
You can access the HCL Launch server in a Kubernetes cluster.

Installing
An HCL Launch installation consists of the HCL Launch server, a database, and at least one agent.
- System requirements and performance considerations
  The HCL Launch server runs on Windows™ and UNIX™ systems. Following some guidelines can improve the performance of the server and agents.
- Firewall and communication configuration
  This topic describes the communication between the HCL Launch components, the firewall, and the ports involved in the communication.
- Installing the server database
  HCL Launch requires a database. You can use the following database types for an evaluation or production server.
- Installing the server
  The server provides services such as the user interface used to configure application deployments, the workflow engine, the security service, and the artifact repository, among others. Installing the server involves specifying configuration information for the server, such as the ports that the server uses.
- Installing with Kubernetes
  The HCL Launch server can be installed in a cloud-based environment, as a containerized server cluster, managed by Kubernetes. HCL Launch works with Kubernetes to simplify application deployment and manage versions in the containers.
  - Installing the server in Kubernetes cluster
    You can install a containerized version of the HCL Launch server in a Kubernetes cluster. The HCL Launch server is installed using a Helm chart.
  - Accessing the HCL Launch server in a Kubernetes cluster
    You can access the HCL Launch server in a Kubernetes cluster.
- Installing agents
  You can install agents from the server or from the command line on the agent system. To configure a failover server for an agent, you must install the agent from the command line.
- Installing agent relays
  An agent relay is a communication proxy for agents that are located behind a firewall or in another network location. You can install agent relays in interactive mode or in silent mode.
- Installing plug-ins
  Plug-ins can be installed at any time. You do not need to restart the server after you install a plug-in.
- Starting HCL Launch
  Both UNIX™ and Windows™ installations require the HCL Launch server and at least one agent. If you are using a database other than Derby, make sure that the appropriate driver is installed and configured.
- Installing and uninstalling test fixes (patches) from the server
  Test fixes are provided to correct specific issues. They are applied to the server as patches.

Accessing the server in a Kubernetes cluster

You can access the HCL Launch server in a Kubernetes cluster.

Before you begin

Ensure that the HCL Launch server is correctly installed in your Kubernetes environment. See Installing the server in a Kubernetes cluster.

About this task

The output of the helm status <releaseName> -n <namespace> command provides commands that contain the URL of your server.

Procedure

Run the commands to obtain the server's URL:

$ helm status launch73111155303 -n launch73111155303

Where, launch73111155303 is the <releaseName> and the <namespace>.

The following output message is displayed and shows the application availability at the echo command:

NAME: launch73111155303
LAST DEPLOYED: Wed May 17 20:08:45 2023
NAMESPACE: launch73111155303
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
It may take a few minutes for the LoadBalancer IP to be assigned. You can watch the status by running:
  kubectl get svc -n launch73111155303 launch73111155303-hcl-launch-server-prod -w

Once the IP is assigned the application will be available at:
  echo https://$(kubectl get svc -n launch73111155303 launch73111155303-hcl-launch-server-prod -o jsonpath='{.status.loadBalancer.ingress[0].ip}'):8443

Note:

To function correctly, you must set the HCL Launch server to External Agent URL and External User URL

These settings are based on the LoadBalancer IP shown in the output message. You can update the settings from the HCL Launch server admin interface on the System Settings tab. Click Settings > System Settings.

Run the echo command displayed in the output message to identify the URL to use to access the HCL Launch server:
```
$ echo https://$(kubectl get svc -n launch73111155303 launch73111155303-hcl-launch-server-prod -o jsonpath='{.status.loadBalancer.ingress[0].ip}'):8443
```
The output of the command displays the server URL:
```
https://x.x.x178:8443
```
You can access the HCL Launch server using the URL output of the echo command.